default to CertificateValidity::INVALID
authorCaolán McNamara <caolanm@redhat.com>
Mon, 8 Feb 2021 17:05:28 +0000 (17:05 +0000)
committerRene Engelhard <rene@debian.org>
Sun, 28 Aug 2022 17:22:27 +0000 (18:22 +0100)
commitd7c1a194456e4694eba3029dda4fd821233d37bf
tree7278faef20cc91b83a24a3d7f995a1c5af178120
parent59a7b2c987d68678143c5b7169a11761947f33b9
default to CertificateValidity::INVALID

so if CertGetCertificateChain fails we don't want validity to be
css::security::CertificateValidity::VALID which is what the old default
of 0 equates to

notably

commit 1e0bc66d16aee28ce8bd9582ea32178c63841902
Date:   Thu Nov 5 16:55:26 2009 +0100

    jl137:  #103420# better logging

turned the nss equivalent of SecurityEnvironment_NssImpl::verifyCertificate
from 0 to CertificateValidity::INVALID like this change does

Change-Id: I5350dbc22d1b9b378da2976d3b0abd728f1f4c27
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/110561
Tested-by: Jenkins
Reviewed-by: Miklos Vajna <vmiklos@collabora.com>
Gbp-Pq: Name default-to-CertificateValidity::INVALID.diff
xmlsecurity/source/xmlsec/mscrypt/securityenvironment_mscryptimpl.cxx